Release 10.1A: OpenEdge Development:
Progress Dynamics Advanced Development

Adding your manager to the session types

Start your manager with one of the framework’s session types by adding to the list of that Session Type’s Required Managers.

To add your manager to the list of that Session Type’s Required Managers:

Open the Session Type Control window from the Session menu, as shown:



You can either create new session types to define different configurations for the client or server or add your manager to more session types. To add the Test Manager to the Default Session Type, select the Default Session Type, select the Edit button, and select the Required Managers tab. The list of session manager procedures appears, as shown:

There are some special things to note about the list of managers:

Progress Dynamics Session Startup — The standard startup procedure for any Progress Dynamics session is icfstart.p. This procedure runs the procedure af/app/afxmlcfgp.p, the Configuration File Manager, which opens and parses the XML configuration file containing all the rest of the information about the session. The Configuration File Manager starts the rest of the managers. In some cases it might not make a difference which order a manager is started in, except that the Connection Manager must always be first in the list, because it is responsible for starting any databases and AppServers, and then getting the rest of the managers started. Ordinarily you simply add a new manager to the end of the list, so make sure you note the number of managers that are already associated with your session type, and assign yours the next higher sequence number.
Manager Procedure Name — Note the name of the manager procedure that appears in the list. There is just one version of the Connection Manager, so it will always appear as afconmgrp.p. The other managers, however, have both a client part and a server part, which conform to the naming convention afxxxsrvrp.p and afxxxclntp.p, where xxx represents a three-letter code for the manager. A given session type runs either on the client or on the server, and must start the appropriate manager procedures for its side of the connection. A stand-alone session runs the server-side managers. Note that this is different from the way that SDOs and other DB-AWARE objects work. In an SDO, you always specify the base name of the object, which runs on the server, and the internals of the constructObject code determine whether to run that or the client proxy. The client proxy, in turn, is responsible for running the server-side object and maintaining a connection to it.

Because managers run explicitly on client or server, you must specify the correct name of the client-side or server-side manager procedure when you add it to the session. You can see from the list of managers for the default session, for example, that because it runs as a stand-alone session, without the AppServer (and therefore without a separate client session), it runs the server versions of the managers.

A client-side Session Type, by contrast, such as the ICFRuntime session, runs the client-side procedures, as shown:

You are now ready to add a manager.

To add your manager once you have selected the Session Type:

Select the Manager tab from the Session Type Maintenance folder.
Select the Add button inside the tab folder to add your manager to the Session, as shown:



Select Test Manager from the pre-populated list of Manager Type lookup.
Enter the Object Filename, which is either the client procedure or the server procedure. Note that you do not have to specify a path to the procedure, because it has already been registered in the Repository, so the Configuration File Manager will be able to locate it from its description as stored in the Repository.
Enter the next available Startup Order sequence for the manager.
Check the System Owned toggle box on if you want only users with System authorization to be able to modify its information.
Choose File Save to add your manager to the list, and close the Session Type Maintenance window.

The description of your manager is now in the Repository, but in order for it to be found when the session starts up, you must add the same information to the XML configuration file that all sessions read in when they start up.

Return to the Session Type Control window and select Option Generate Configuration File to rebuild the XML file from the Repository data, as shown:



At the prompt, enter the name of the configuration file, and choose either Local File or Remote File, depending on whether the file is local to your machine or remote. The default file is icfconfig.xml, in the src directory where your Progress Dynamics code was installed. Move the file to another location in your application’s ProPath if you are going to modify it.
After setting the Filename, choose Generate, as shown:



The generated configuration file appears, as shown:



This file contains the information for the Test Manager added to the Default session (a number of nodes in the XML information are not expanded here, so that you only see what has been added).